Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't allow activities if the subscriber is current, or the connection to Kinesis is broken #374

Merged
merged 3 commits into from
Aug 20, 2018

Conversation

pfifer
Copy link
Contributor

@pfifer pfifer commented Aug 20, 2018

Issue #, if available:

Description of changes:
There is a possibility that the flow can become null while a request is inflight. This would cause an NPE. The KCL will recover in this case, but the recovery would be delayed.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

pfifer added 3 commits August 20, 2018 11:50
Calls to Subscription#request weren't synchronized correctly.  This
was only really an issue if there is a large number of errors
occurring.
If the original subscriber doesn't match the current subscriber reject
operations completely.
If the flow is null, but the subscriber still matches error out the
subscription.  The original subscriber will restart.

For canceling only accept the cancel request if the original
subscriber matches the current subscriber.
Don't really need to check if the subscriber is still current, as this
is synchronized.
@pfifer pfifer added this to the v2.0.1 milestone Aug 20, 2018
@sahilpalvia sahilpalvia merged commit 5533d37 into awslabs:master Aug 20, 2018
@pfifer pfifer added the v2.x Issues related to the 2.x version label Aug 20, 2018
pfifer added a commit to pfifer/amazon-kinesis-client that referenced this pull request Aug 21, 2018
Ordered the release notes in ascending order of their issue #

Added release notes for awslabs#374 and awslabs#375
sahilpalvia pushed a commit that referenced this pull request Aug 21, 2018
* Update release notes for release 2.0.1

* Updated version to 2.0.1

* Added notes for PR #371, and cleaned up formatting

* Reordered release notes, and added additional fixes

Ordered the release notes in ascending order of their issue #

Added release notes for #374 and #375

* Add release notes to the change log
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2.x Issues related to the 2.x version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants